System and method for generating use statistics for location-based applications

ABSTRACT

A system for analyzing the use of location-based service applications including: a mobile device. A carrier-positioning infrastructure interacts with the mobile device for enabling the use of location-based applications by the mobile device. A mobile location-based application provider communicates with the carrier-positioning infrastructure to provide a location-based application to the mobile device. A location transaction platform monitors the use of the location-based application by the mobile device. An analytics server communicates with the location transaction platform and location stamps an occurrence of use of the location-based application by the mobile device and performs a task in accordance with predetermined rules as a function of the location-based stamp.

PRIORITY CLAIM/RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.12/961,117, filed Dec. 6, 2010, which claims priority under 35 USC 120and is a divisional of U.S. patent application Ser. No. 11/805,078 filedon May 22, 2007 and entitled “System And Method For Generating UseStatistics For Location-Based Applications” which in turns claims thebenefit under 35 USC 119(e) to U.S. Provisional Patent Application No.60/830,367 filed on Jul. 12, 2006 and entitled “System And Method ForGenerating Use Statistics For Location-Based Applications”, the entiretyof which are incorporated herein by reference.

FIELD

The present invention is directed to a system and method for trackinglocation-based application use, and more particularly, for generatingdata of such use as a function of geographic location.

BACKGROUND

The use of location-based services or applications for portable devices,most commonly in a cellular telephone network, have become widespread.These are services or applications that are provided to subscribersbased on their current geographic location. Such applications areLOC-AID® People™, which allows one user to know the location of anotheruser merely by dialing the target user's cellular phone number andLOC-AID® GEO-FAM™ an application for notifying a user when the cellphone of another user has either entered or left a predeterminedgeographical region. These location-based applications provided byLOC-AID Technologies, Inc. are by way of example only. Otherlocation-based applications may identify certain commercialestablishments within a predetermined area of the cellular phone or mayeven respond to queries from the cellular phone user as to places ofinterest or people of interest.

For end users of location-based services, the technology althoughdeveloping has been satisfactory, as evidenced by the growing number oflocation-based service users. However, for location-based servicedevelopers and for commercial entities making use of location-basedservices to drive traffic to their establishments, the current model forlocation-based service use has been less than satisfactory.Specifically, location-based services as provided on cellular phones aredriven by the actual location of the user at the time of use of thelocation-based service. Developers of location-based services developthese applications in response to a perceived need. But in actuality,they design these applications in a vacuum because there is no feedbackwith respect to how the applications are actually used. Although thenumber of times a location-based application may be monitored, and insome cases the time of use may be monitored, there is no monitoringwhere the application is being used. Because these applications arelocation driven this is a vital statistic for monitoring applicationadoption and use.

Furthermore, in some instances these location-based applications arecreated to direct traffic to a specific location such as a restaurant,store or other point of interest to the end consumer of thelocation-based application. In order to better develop marketingschemes, these location entities need to know where the users of thelocation-based applications are in fact located when using anapplication designed to motivate that user to visit their location.

Accordingly, a methodology and system which overcomes the shortcomingsof the prior art by providing information regarding use oflocation-based applications as a function of the geographic location ofthe user when making use of the location-based application is desired.

SUMMARY

A location-based services applications provider provides alocation-based service application to be utilized at a mobile device. Amobile device performs the location-based service provided by theapplication provider. The mobile device is located within a positioninginfrastructure for determining the location of the mobile device whenutilizing a location-based services application. An analytic server isprovided in communication with the positioning infrastructure todetermine the location of the mobile device as it utilizes thelocation-based service and location stamps the use of the respectivelocation-based service applications and stores the geostamp for thelocation-based application usage. The analytical server performs a taskin accordance with rules as a function of the geostamp of thelocation-based service application.

In a preferred embodiment, the analytic server creates a report of useof location-based applications as a function of the location of themobile device during use of the location-based service. In anotherembodiment, the analytic server may cause a message to be sent to themobile device as a function of the geostamp associated with thelocation-based service application.

BRIEF DESCRIPTION OF THE DRAWINGS

For a fuller understanding of the invention, reference is had to thefollowing description taken in connection with the following drawings inwhich:

FIG. 1 is a schematic diagram of a system for analyzing and performing atask in response to use of location-based service applications inaccordance with the invention;

FIG. 2 is an operational diagram showing an analytic server performingtasks in accordance with the rules in accordance with the invention.

FIG. 3 is a schematic diagram of the functional components of theanalytic server in accordance with the invention; and

FIG. 4 is a flow chart for tracking metrics for a location-based game inaccordance with the invention.

DETAILED DESCRIPTION OF ONE OR MORE EMBODIMENTS

Reference is made to FIG. 1 in which a system, generally indicated as10, for analyzing and performing tasks in response to geographical datacollected with respect to the use of location-based service applicationis provided. System 10 includes an application source 12. Applicationsource 12 is the application provider, i.e., the developer and source oflocation-based service applications. In one contemplated embodiment, theapplication provider may be the server for an application serviceprovider. The application service provider may be any one of a gamesapplications provider 14, a community applications provider 16, by wayof example FIND ME™, or an instant message chat-type of applicationsprovider 18. It should be understood that the applications may also bedownloaded as is known in the art to mobile device 20 such as a cellularphone.

Mobile device 20 communicates with location-based application source 12across a carrier positioning infrastructure 50 as known in the art. Anexemplary, but non-limiting example of such a carrier positioninginfrastructure 50 may include a position determining entity (“PDE”)server 52 working in cooperation with a mobile positioning center(“MPC”) 54 utilizing protocols to communicate between the mobileapplication provider server 12 and mobile device 20. However, it shouldbe noted that PDE 52 and MPC 54 may be any position-determiningarchitecture such as a general mobile locating center 56 or a specificmobile locating center 58. The actual configuration is determined as afunction of the communication technology or location technology utilizedwithin carrier positioning infrastructure 50.

To facilitate the use of the location-based service application bymobile device 20 in a preferred embodiment, certain infrastructure isutilized. In one embodiment, it has been recognized that applicationproviders are not capable of designing a location-based serviceapplication capable of communicating across all communication platforms,all communication carriers and the various associated protocols.Accordingly, a location development portal 30 provides infrastructurewhich allows the location-based service application provider to createlocation-based applications capable of interacting with substantiallyany mobile device across any mobile carrier as known from applicant'sco-pending U.S. Provisional Application No. 60/715,848, which isincorporated as if fully set forth herein.

Once an application has been developed, there are still othercompatibility issues. Each country, even each service carrier, developsits own protocols for using wireless services. Carriers may even use aplurality of location-based platforms or technologies within a network.Furthermore, as a result of the proprietary nature of carrier networks,one carrier may not allow another carrier to provide location-basedservice on its network, i.e., the protocols and technologies aredesigned to be cross-incompatible. To alleviate this issue, a gateway 40as known from applicant's co-pending U.S. application Ser. No.11/394,681 (referenced as if incorporated fully herein) is provided toallow communication and use of the location-based service applicationacross a plurality of carrier positioning infrastructures.

A location transaction platform 60 is in communication with the carrierpositioning infrastructure and monitors use of location-based servicetransactions, i.e., each occurrence of the use of a location-basedservices application by a mobile device 20. Location transactionplatform 60, at a minimum, notes the application and the location atwhich the application is utilized for each use of the location-basedservice application for each respective mobile device 20 being monitoredand location stamps the use of the location-based application. In otherwords, it marks the longitude and latitude (“geostamps” or “locationstamps”), or physical map location of the use of the location-basedapplication by mobile device 20, which in a preferred embodiment is acellular phone. The user may geostamp themselves by sending theirlocation or confirming that they are at an expected location (even ifinaccurate).

In a preferred embodiment, several types of application information maytravel with the utilization of the location-based service such as thetime and date of the use, the identity of the provider of theapplication, or the identification of the user (whether by name, numericID, phone number or the like) by way of non-limiting example.

In another embodiment, the application information may includeinformation related to the utilization of a location-based application,for example, a gaming application. By way of a non-limiting example, thegaming application may be a treasure hunt in which gamers are directedto a venue to search for objects and win prizes for finding andretrieving the objects. A venue is a physical location for thelocation-based application, for example, a city park, an address, or alatitude, longitude geographic coordinate. The venue may include aphysical area or place were events of a specific type are held, forexample, a city block delineated by streets or street intersections, ora radial distance from an address. The location-based application caninclude one or more venues, for example, a grocery store, a parkinggarage, or a waypoint venue on the way to a final destination venue. Forexample, the treasure hunt may include a first venue, such as, 123 MainStreet, where gamers are instructed to find an object, for example, anenvelope. The gamers may be provided a tip or hint for finding theobject, for example, “check under the sign for product X.” Gamers can bedirected toward a second venue, and third venue, and so on, until theycomplete the treasure hunt.

By way of another example, the location-based application may be aconference trivia contest for which users are directed to select asponsor and instructed to go a to venue of the selected sponsor. Forexample, the venue may be the selected sponsor's exhibit booth whereusers are presented with trivia questions.

The location transaction platform 60 may accept messages from alocation-based application user, for example, a message from thetreasure hunt game user or trivia contest player, described above. Inone embodiment, the message may be a message that a mobile device userhas opted to participate (or to not participate) in a location-basedapplication. In another embodiment, the message may be a message that amobile device user has opted to engage (or to not engage) in alocation-based venue. In still another embodiment, the message may be amessage that a mobile device user is at a location-based applicationvenue.

Location transaction platform 60 is further in communication withanalytics server 70 associated with a database 88. Analytics server 70receives the location stamp and associated application information fromthe location transaction platform 60. Analytics server 70 stores theinformation in a database 88. The rules of operation of analytics server70 are also stored in database 88. These rules govern the tasksperformed by analytics server 70 as a function of the location stamp andassociated application, which will be discussed in greater detail below.

Reference is now made to FIG. 3 in which a functional diagram ofanalytics server 70 is provided. Analytics server 70 includes ananalytics generator 80 for operating on geostamped data and inputmanager 72, which provides inputs to be operated upon by the analyticsgenerator 80. An interface handler 90 provides input to and receivesoutput from the analytics generator 80. The display delivery manager 100determines when and what type of output the analytics server 70 willprovide as a function of the rules.

In a generic sense, analytics server 70 accepts and operates ongeographically framed queries and generates demographic data of whereusers are geographically when they interact with a location-basedservice application. The queries may take several forms such as, whereis the use of the location-based service application relative to a pointof interest? where is the location-based service application userelative to a geographic boundary? what is the demographic? (how closeis the use to a store or landmark of interest) (are a significant numberof uses coming from a specific one or more geographic area? such ascollege campuses, public parks, by way of non-limiting examples).Furthermore, the query can be made more sophisticated to layer on timeand date information to the geographical queries, or even where allowed,demographic data with respect to the users.

Analytics server 70 may manipulate this data and determine things suchas which location-enabled applications are utilized more frequently,which networks are utilized for more location-based transactions, wherethe location of location-based application or person-to-personinteraction is utilized, and where the users of a location-based serviceapplication of interest are located.

Analytics server 70 operates in accordance with rules as a function ofthe information garnered. By way of non-limiting example, it acts ongeographically framed queries such as creating a map to determine wherethe users are located when they interact with a particularlocation-based service application or demonstrate how far away they arefrom one of the points of interest. Analytics server 70 may delivermap-oriented or text-based statistics. In another embodiment, analyticsserver 70 may provide interactive feedback triggered by the use of alocation-based service application as a function of the location of theuser. By way of non-limiting example, if the location-based serviceapplication is to determine the proximity of a user to a point ofinterest such as a coffee shop, analytics server 70 determines thelocation of the user by determining the location of the mobile deviceand when the mobile device 20 is within a predetermined distance of thelocation of interest. Analytics server 70 may cause location transactionplatform 60 to initiate a secondary location-based service applicationsuch as providing an alert to the mobile device 20 that they are inproximity of the coffee shop, a coupon for use at the coffee shop, orinformation such as a menu or sales prices, by way of non-limitingexample.

Reference is again made to FIG. 3 where an operational diagram isprovided to describe the function of the analytics server 70 in greaterdetail. Analytics server 70 includes input manager 72 which provides thefunctionality of data ingest at a data ingest 73, which includes theplaces of interest such as museums, stores, restaurants, movie theatersor the like. Input manager 72 also performs the parsing and constructionof queries of interest to users of analytics server 70 at a queryconstructor and parser 75. These queries may be, where does alocation-based application of interest get utilized? over which networksdoes the location-based application get utilized? where is thelocation-based application being utilized? how far away are the uses ofthe location-based application from a place of interest? by way ofnon-limiting example. The queries and data are input to analyticsgenerator 80.

Analytics generator 80 spatially correlates the data and schedules tasksby performing the rules. Analytics generator 80 includes a spatialcorrelator 82 which compares locations in accordance with the query. Itdetermines whether the query applies, i.e., is the use of thelocation-based application at a geographical location of concern or hasconfirmation from the cellular phone been received. A rules engine 84applies the rule such as those discussed above. As scheduler 86 acts asthe gateway scheduling the application of the rules by determining whena location-based service application use is occurring and as a functionof the rules engine 84, either realtime triggers or accumulation of usedata, schedules the output from analytics generator 80 prescribed by therules as determined by rules engine 84. By way of non-limiting example,scheduler 86 may allow analytics generator to perform the task inaccordance with the rules as a function of an instantaneous realtimetrigger, i.e., query has been applied, rule indicates that a responsemust be immediately performed, such as a rule that a secondarylocation-based application must be sent to mobile device 20 in responseas a function of the query—“Is the mobile device within a predeterminedgeographical area or near a geographical place of interest”. On theother hand, scheduler 86 may release the application of the rule as afunction of the aggregated number of data points or elapsed time. Thisrelease may be in response to a query such as “where or when are thegreatest number of uses of the application of interest”. This wouldrequire a meaningful sampling and therefore would require aggregation ofmultiple data points, not a single data point causing scheduler toaccumulate occurrences before performance of the task in accordance withthe rules.

By way of example, the location-based application can be the treasurehunt game described above. As shown in FIG. 4, the location-basedapplication may send to mobile device users, for example, mobile deviceusers registered with a wireless carrier service, an invitation in step400 to participate in the activity. For example, the invitation can be“Do you want to play the Product X Treasure Hunt Challenge?” Mobiledevice users can receive the invitation message in step 402 and send aparticipation message in step 404 in response to the invitation, forexample, by selecting on their mobile device an option to participate oran option to not participate and selecting “send response.”Alternatively, users may ignore the campaign message, in which case noparticipation message is sent. The participation message is accepted bya location transaction server in step 406. The location transactionserver can accept a plurality of participation messages from mobiledevice users responding to the invitation message. The number ofinvitation messages sent in step 400 and the number of participationmessages received (and the selection) in step 406 can be stored in steps401 and 407, respectively, in the system in a memory, for example, acomputer hard drive or a compact disk.

The location-based application can send to participating mobile deviceusers a menu of game venue options in step 408, for example, a list oflocations (Bob's Barber Shop, Jim's Diner, etc.) for the treasure huntgame or a list of sponsors (Company X, Company Y, etc.) for theconference trivia contest. The mobile device users can receive the venueoptions in step 410 and send an engagement message to opt-in or opt-outof a particular venue option in step 412. For example, the user canselect, “Bob's Barber Shop” and “opt-in.” The location transactionserver can accept the engagement message in step 414. The number ofengagement messages received is stored in step 415 in the system memory.

The location-based application can send to engaged mobile device usersan instruction to proceed to the selected venue in step 416. Forexample, the instruction can be, “Proceed to 123 Main Street.” Themobile device users can receive the instruction in step 418 and choosewhether to follow the instruction. For example, the mobile device userscan proceed to 123 Main Street. In one embodiment, a mobile device usercan send an at-venue message to the system in step 420 to inform system10 that the mobile device user is at or near the venue. In still anotherembodiment, system 10 can automatically track the user's location anddetermine if the user is at or near the venue. The location transactionserver can accept the at-venue message in step 422. The number ofat-venue messages received is stored in step 423 in the memory.

The location transaction server can send further instructions in step424 related to the location-based application and venue. For example,the instruction may be related to the treasure hunt game, for example,“Find white envelope.” The instruction can include a tip, for example,“Check under the sign for Product X.” Mobile device users receive theinstructions in step 426 and send a response in step 428. The locationtransaction server can accept the response and completion of theat-venue instruction in step 430. The number of completion messagesreceived is stored in step 431 in the memory. The location transactionserver can complete the game or offer instructions to play again in step432 for multiple at-venue game sequences or loops.

An analytics server 70 can perform tasks to compute a variety of metricsusing predefined rules as a function of location-based applicationinformation. In one embodiment, the metric may be a participation raterelated to accepted participation messages. In another embodiment, themetrics may be an engagement rate related to accepted engagementmessages. In still another embodiment, the metric may be an at-venuemetric related to accepted at-venue messages described above. Thelocation transaction platform 60 communicates message information to theanalytics server 70, which is associated with a database 88. Theanalytics server 70 stores the information in the database 88 (memory).The analytics server 70 computes the metrics according to the predefinedrules. For example, the message information may be the number ofcampaign invitations sent to mobile users stored in step 401, the numberof mobile device users who opted to participate in the campaign storedin step 407, the number of mobile device users who selected alocation-based venue stored in step 415, or the number of mobile deviceusers who indicated they were at a venue stored in step 423.

By way of example, the location transaction platform 60 can communicatethe number of campaign invitations (NO_INVS) sent to mobile devicesusers and the number of mobile device users who opted to participate inthe campaign (NO_PARTS). The analytics server 70 can compute theparticipation rate as the ratio of the NO_PARTS over NO_INVS andmultiply the result by 100 to obtain a percentage value. For example, ifNO_INVS=1000 and NO_PARTS=250, the participation rate is 25%. Theanalytics server 70 can compute the engagement rate as the ratio of thenumber of mobile device users who selected to engage in venues(NO_ENGAGE) over the NO_PARTS. For example, if the NO_ENGAGE=125, theengagement rate is 50%. The analytics server 70 can compute the at-venuerate as the ratio of the number of mobile device users who indicatedthat they were at a venue (NO_VEN) over the NO_ENGAGE. For example, ifthe NO_VEN=75, the at-venue rate is 60%. The formulas for thesecomputations are stored as part of the predefined rules. A venuecompletion rate can also be computed, for example, the percentage ofmobile device users who completed the venue.

The interface handler 90 includes three interfaces. The first interfaceis the realtime application interface 92, which is the output interfaceto the portable device 20, or the receiver of the report. Thetransaction interface 94 is the input interface which monitors theoccurrence of the location-based services input and may also monitor thedata associated with the location-based service application occurrence.Because of the nature of geographical location-based services, ageographic interface 96 interacts with that portion of the carrierpositioning infrastructure 50, third party map source, or location basedservice application provider which provides map and locationinformation. The interface handler 90 communicates with the analyticsgenerator 80 to provide the data utilized by spatial correlator 82received at realtime application interface 92 and geographic interface96.

The transaction interface may receive occurrence information related tovenues for a location-based application as described above. For example,the occurrence information may be a participation message, an engagementmessage, an at-venue message, or a venue completion message as describedabove. The analytics server may receive the occurrence information tocompute campaign metrics, for example, a participation rate, anengagement rate, an at-venue rate, and a completion rate as describedabove.

Lastly, display/delivery manager 100 communicates with both analyticsgenerator 80 and interface handler 90. Display/delivery manager 100includes a trigger manager 102, which determines whether all theconditions were met to trigger the task in accordance with the rulesengine 84 and the query. The trigger manager operates in response to asignal from scheduler 86. If the trigger manager 102 determines that aresponse to the output is proper, it reports in one of at least threeexemplary ways. An alert engine 104 may be triggered to send an alert ofuse through interface handler 90 that a condition of interest hasoccurred. As discussed above, rules engine 84 may create a report inresponse to a query and trigger manager 102 may cause report generator106 to create the desired report, which is then output through realtimeapplication interface 92 to the desired recipient, normally the providerof the location-based application or the owner of the place of interest.As discussed above, in some instances, rules engine 84 determines thatan instantaneous location message or other location-based serviceapplication should be sent to mobile device 20. In this case, triggermanager 102 causes transmission of the output of rules engine 84 totransaction interface 94 and on to mobile device 20 utilizingtransmitter 108.

Reference is now made to FIG. 2 wherein a functional diagram of theoperation of analytics server 70, like numbers are utilized to indicatelike structure or functionality. As discussed above, during use, theoccurrence of a location-based services application transaction iscommunicated from location transaction platform 60 to analytics server70. In accordance with the rules, analytics server 70 performs a task,either analyzing geographic data, creating a data-driven report 200 orperforming a non-reporting function such as a realtime trigger toprovide a secondary location-based application to mobile device 20.

Analytics server 70 provides data-driven reports such as map-basedreports 210, which may take the form of two dimensional or threedimensional plotting of occurrences on a map grid. It may be astatistics report 212 which would take the form of statisticscorrelating application use, and location of such use, and optionallytime of such use, and other demographics of such use. Lastly, a report214 may take the form of a raw data dump, merely being a printout ofeach of the data points as determined by analytics server 70.

On the other hand, in accordance with the rules, analytics server 70 mayoutput a realtime trigger to mobile application developers 12 formonitoring purposes or for an appropriate location-based serviceapplication to be sent to mobile device 20 in response to an occurrenceof a predetermined geographical location-based criteria for a particularlocation-based systems application.

It should be noted that for those instances where necessary the locationdevelopment portal 30 and location gateway 40 may be utilized to enableanalytics server 70 to communicate with the mobile applicationsproviders 12. However this is not necessary for performance of theinvention. It should also be noted that a generic mobile device 20 wasutilized. However, mobile device 20 is preferably a cellular phone butmay be a personal digital assistant, automatic vehicle location ID orthe like. Furthermore, database 88 is shown as associated with analyticsserver 70. However, it should be readily understood that it is withinthe concept of the invention, as each element of a system is within acommunications network, that the functionality and the data storage oranalytics analysis may be distributed across the network. Conversely, itis well within the scope of the invention to combine the functionalityof analytics server 70 and location transaction platform 60 into asingle location or server.

By providing an analytics server, which location stamps location-basedservice application use by mobile devices, a new analytic and customerservice tool is provided. It provides marketing advantages byidentifying geographically based hot spots for location-based systemapplication uses which enables campaign response feedback and usefeedback; allowing developers and marketers to tweak the applications tobetter serve the needs of the end user. By triggering actions withrealtime triggers which cause the use of secondary or responsivelocation-based service applications, push marketing is enabled to marketto those people who are already within a meaningful distance of a placeor service of interest.

Thus, while there have been shown, described, and pointed out novelfeatures of the present invention as applied to preferred embodimentsthereof, it will be understood that various omissions and substitutionsand change in the form and detail are contemplated and may be made bythose skilled in the art without departing from the spirit and scope ofthe invention. It is the intention therefore to be limited only asindicated by the scope of the claims appended hereto. It is also to beunderstood that the following claims are intended to cover all of thegeneric and specific features of the invention herein described and allstatements of the scope of the invention, which, as a matter of thelanguage, might be said to fall therebetween.

The invention claimed is:
 1. A system for analyzing a use of alocation-based service application within a mobile network comprising: alocation transaction platform for monitoring the use of thelocation-based application by a plurality of mobile devices andreceiving occurrence information including a location of each of theplurality of mobile devices during the use of said location-basedapplication and a time for each respective use; a processor foraggregating the received occurrence information for said location-basedapplication; an input manager for receiving a request for specificanalytic information for said location-based application and its users;and an analytics generator communicating with said location transactionplatform for receiving the aggregated occurrence information regardingthe occurrence of the uses of said location-based application by theplurality of mobile devices, communicating with the input manager forcomparing the location of the mobile devices during use of saidlocation-based application, and scheduling a task based on theaggregated occurrence information for the location-based application. 2.The system of claim 1, further comprising a display/delivery manager fortriggering the scheduled task.
 3. The system of claim 1, wherein thetask is creating a report regarding the use of said location-basedapplication by the plurality of mobile devices.
 4. The system of claim3, wherein the report is one of a two-dimensional or three-dimensionalmap.
 5. The system of claim 3, wherein the report is a text reportproviding statistics of the use of said location-based application bythe plurality of mobile devices as a function of location.
 6. The systemof claim 3, wherein the report is raw data of the use of saidlocation-based application by the plurality of mobile devices.
 7. Thesystem of claim 1, wherein the task is causing a mobile applicationprovider to provide another location-based application to a mobiledevice.
 8. The system of claim 1, wherein said scheduling a task is alsobased on a plurality of predetermined rules.
 9. The system of claim 8,wherein at least one of the predetermined rules is determining wheresaid location-based application is used over a period of time.
 10. Thesystem of claim 8, wherein at least one of the predetermined rules iswhere the occurrence of use of said location-based application isrelative to a place of interest, or determining the location of theoccurrence of the use of said location-based application relative to ageographical area.
 11. The system of claim 1, wherein the occurrenceinformation further comprises a venue for the location-basedapplication, and an engagement message for communicating an engagementin the venue.
 12. The system of claim 11, wherein the task is computingan engagement rate for the venue.
 13. A method for analyzing a use of alocation-based service application within a mobile network comprising:monitoring the use of the location-based application by a plurality ofmobile devices; receiving occurrence information including a location ofeach of the plurality of mobile devices during the use of saidlocation-based application and a time for each respective use;aggregating the received occurrence information for said location-basedapplication; receiving a request for specific analytic information forsaid location-based application and its users; receiving the aggregatedoccurrence information regarding the occurrence of the uses of saidlocation-based application by the plurality of mobile devices; comparinglocations of the mobile devices during use of said location-basedapplication; and scheduling a task based on the aggregated occurrenceinformation for the location-based application.
 14. The method of claim13, further comprising a triggering the scheduled task.
 15. The methodof claim 13, wherein the task is creating a report regarding the use ofsaid location-based application by the plurality of mobile devices. 16.The method of claim 15, wherein the report is one or more of atwo-dimensional map, a three-dimensional map, text report providingstatistics of the use of said location-based application by theplurality of mobile devices as a function of location, and raw data ofthe use of said location-based application by the plurality of mobiledevices.
 17. The method of claim 13, wherein the task is causing amobile application provider to provide another location-basedapplication to a mobile device.
 18. The method of claim 13, wherein theoccurrence information further comprises a venue for the location-basedapplication, and an engagement message for communicating an engagementin the venue.
 19. The method of claim 18, wherein the task is computingan engagement rate for the venue.
 20. The method of claim 13, whereinsaid scheduling a task is also based on a plurality of predeterminedrules, and at least one of the predetermined rules is determining wheresaid location-based application is used over a period of time.